Administering devices including allowed action lists

ABSTRACT

Exemplary embodiments of the present invention include a method for administering devices in a network. The method includes creating a user metric vector comprising a plurality of disparate user metrics, creating a user metric space comprising a plurality of metric ranges and determining whether the user metric vector is outside the user metric space. If the user metric vector is outside a user metric space, identifying an action in dependence upon the user metric vector the method includes determining whether the action is allowed. If the action is allowed, the method includes executing the action. Many embodiments include receiving an allowed action list, such as for example, receiving an allowed action list from a moderator DML.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation application of and claims priorityfrom U.S. patent application Ser. No. 10/692,414 now U.S. Pat. No.7,461,143 filed on Oct. 23, 2003.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The field of the invention is data processing, or, more specifically,methods, systems, and products for administering devices.

2. Description of Related Art

Conventional networks contain various devices. A user often uses thevarious devices, or adjusts the particular settings of the devices independence upon the user's current condition. That is, a user's currentcondition often motivates the user to change the settings of devices sothat the devices operate in a manner that more positively benefits theuser's current condition. For example, a user with a headache may bedisturbed by a powerful light. The user may dim the light, or turn thelight off, so that the light no longer disturbs the user. Conventionalnetworked devices, however, require user intervention to individuallyadminister the specific device in response to user condition. It wouldbe advantageous if there were a method of administering devices independence upon user condition that did not require user intervention.

SUMMARY OF THE INVENTION

Exemplary embodiments of the present invention include a method foradministering devices in a network. The method includes creating a usermetric vector comprising a plurality of disparate user metrics, creatinga user metric space comprising a plurality of metric ranges anddetermining whether the user metric vector is outside the user metricspace. If the user metric vector is outside a user metric space,identifying an action in dependence upon the user metric vector themethod includes determining whether the action is allowed. If the actionis allowed, the method includes executing the action. Many embodimentsinclude receiving an allowed action list, such as for example, receivingan allowed action list from a moderator DML.

In typical embodiments of the present invention, determining whether theaction is allowed includes comparing the identified action with anallowed action list. Many embodiments include identifying an allowedreplacement action, if the identified action is not allowed andexecuting the allowed replacement action. In many such embodiments,identifying an allowed replacement action includes comparing theidentified action with an allowed action list.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of exemplary embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an exemplary architecture usefulin implementing methods for administering devices in accordance with thepresent invention.

FIG. 2 is a block diagram illustrating an exemplary services gateway.

FIG. 3 is a block diagram illustrating exemplary classes useful inimplementing methods for administering devices in accordance with thepresent invention.

FIG. 4 is a class relationship diagram illustrating an exemplaryrelationship among the exemplary classes of FIG. 3.

FIG. 5 is a data flow diagram illustrating an exemplary method ofadministering devices in accordance with the present invention.

FIG. 6 is a data flow diagram illustrating an exemplary method ofexecuting an action.

FIG. 7 is a data flow diagram illustrating an exemplary method ofdetermining whether a user metric is outside a predefined metric rangefor the user in accordance with the present invention.

FIG. 8 is a data flow diagram illustrating an exemplary method ofadministering devices in accordance with the present invention.

FIG. 9 is a data flow diagram illustrating an exemplary method ofcreating a user metric vector and an exemplary method of creating ametric space.

FIG. 10 is a data flow diagram illustrating an exemplary method ofdetermining whether a user metric vector is outside a user metric space.

FIG. 11 is a data flow diagram illustrating an exemplary method ofcreating a dynamic action list.

FIG. 12 is a data flow diagram illustrating an exemplary method ofadministering devices in accordance with the present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS Introduction

The present invention is described to a large extent in thisspecification in terms of methods for administering devices. Personsskilled in the art, however, will recognize that any computer systemthat includes suitable programming means for operating in accordancewith the disclosed methods also falls well within the scope of thepresent invention. Suitable programming means include any means fordirecting a computer system to execute the steps of the method of theinvention, including for example, systems comprised of processing unitsand arithmetic-logic circuits coupled to computer memory, which systemshave the capability of storing in computer memory, which computer memoryincludes electronic circuits configured to store data and programinstructions, programmed steps of the method of the invention forexecution by a processing unit.

The invention also may be embodied in a computer program product, suchas a diskette or other recording medium, for use with any suitable dataprocessing system. Embodiments of a computer program product may beimplemented by use of any recording medium for machine-readableinformation, including magnetic media, optical media, or other suitablenon-transitory tangible media. Persons skilled in the art willimmediately recognize that any computer system having suitableprogramming means will be capable of executing the steps of the methodof the invention as embodied in a program product. Persons skilled inthe art will recognize immediately that, although most of the exemplaryembodiments described in this specification are oriented to softwareinstalled and executing on computer hardware, nevertheless, alternativeembodiments implemented as firmware or as hardware are well within thescope of the present invention.

DEFINITIONS

“802.11” refers to a family of specifications developed by the IEEE forwireless LAN technology. 802.11 specifies an over-the-air interfacebetween a wireless client and a base station or between two wirelessclients.

“API” is an abbreviation for “application programming interface.” An APIis a set of routines, protocols, and tools for building softwareapplications.

“BLUETOOTH™” refers to an industrial specification for a short-rangeradio technology for RF couplings among client devices and betweenclient devices and resources on a LAN or other network. Anadministrative body called the BLUETOOTH™ Special Interest Group testsand qualifies devices as BLUETOOTH™ compliant. The BLUETOOTH™specification consists of a ‘Foundation Core,’ which provides designspecifications, and a ‘Foundation Profile,’ which providesinteroperability guidelines.

“Coupled for data communications” means any form of data communications,wireless, 802.11b, Bluetooth, infrared, radio, internet protocols, HTTPprotocols, email protocols, networked, direct connections, dedicatedphone lines, dial-ups, serial connections with RS-232 (EIA232) orUniversal Serial Buses, hard-wired parallel port connections, networkconnections according to the Power Line Protocol, and other forms ofconnection for data communications as will occur to those of skill inthe art. Couplings for data communications include networked couplingsfor data communications. Examples of networks useful with variousembodiments of the invention include cable networks, intranets,extranets, internets, local area networks, wide area networks, and othernetwork arrangements as will occur to those of skill in the art. The useof any networked coupling among television channels, cable channels,video providers, telecommunications sources, and the like, is wellwithin the scope of the present invention.

“Driver” means a program that controls a device. A device (printer, diskdrive, keyboard) typically has a driver. A driver acts as translatorbetween the device and software programs that use the device. Eachdevice has a set of specialized commands that its driver knows. Softwareprograms generally access devices by using generic commands. The driver,therefore, accepts generic commands from a program and then translatesthem into specialized commands for the device.

“DTMF” is an abbreviation for Dual Tone Multi-Frequency. DTMF systemstransmit signals across existing power lines, telephone lines, orwirelessly by assigning a tone of a particular frequency to each key ofa touch-tone key pad at the signal's origin and converting the tone to avalue at the signal's destination. Many such DTMF systems include a DTMFencoder at the origin that creates the predetermined tone when aparticular key of the DTMF keypad is invoked and a DTMF decoder thatconverts the tone to a value at the destination.

The signal generated by a DTMF encoder is a summation of the amplitudesof two sine waves of different frequencies. In typical DTMF systems,each row of keys on a key pad is assigned a low tone. The first row of akey pad (keys 1, 2, and 3) is typically assigned a low tone of 697 Hz.The second row of a key pad (keys 4, 5, and 6) is typically assigned alow tone of 770 Hz. The third row of a key pad (keys 7, 8, and 9) istypically assigned a low tone of 852 Hz. The fourth row of a key pad(keys *, 0, and #) is typically assigned a low tone of 491 Hz.

Each column of keys on the keypad is assigned a high tone. The firstcolumn of a key pad (keys 1, 4, 7, and *) is typically assigned a hightone of 1209 Hz. The second column of a key pad (keys 2, 5, 8, and 0) istypically assigned a high tone of 1336 Hz. The third column of a key pad(keys 3, 6, 9, and #) is typically assigned a high tone of 1477 Hz.

Pressing a key of a DTMF system's key pad results in the summation ofthe particular key's low tone (assigned by the row in which the keyresides) with the particular key's high tone (assigned by the column inwhich the key resides). For example, pressing ‘1’ on a typical DTMFkeypad results in a tone created by adding 1209 Hz and 697 Hz. Theparticular frequencies of the low tones and high tones have been chosento reduce harmonics when the high tones and the low tones are added.

Many DTMF systems are currently available. For example, off-the-shelfDTMF systems are available from Silicon Systems, Inc., ArkadyHorak-Systems, and Mitel Corp. All such DTMF systems can beadvantageously used with various embodiments of the methods foradministering devices in accordance with the present invention.

“ESN” is an abbreviation for “Electronic Serial Number.” An ESN is aserial number programmed into a device, such as, for example, acoffeepot, to uniquely identify the device.

“Field”—In this specification, the terms “field” and “data element,”unless the context indicates otherwise, generally are used as synonyms,referring to individual elements of digital data. Aggregates of dataelements are referred to as “records” or “data structures.” Aggregatesof records are referred to as “tables” or “files.” Aggregates of filesor tables are referred to as “databases.” Complex data structures thatinclude member methods, functions, or software routines as well as dataelements are referred to as “classes.” Instances of classes are referredto as “objects” or “class objects.”

“HAVi” stands for ‘Home Audio Video interoperability,’ the name of avendor-neutral audio-video standard particularly for home entertainmentenvironments. HAVi allows different home entertainment and communicationdevices (such as VCRs, televisions, stereos, security systems, and videomonitors) to be networked together and controlled from one primarydevice, such as a services gateway, PC, or television. Using IEEE 1394,the ‘Firewire’ specification, as the interconnection medium, HAVi allowsproducts from different vendors to comply with one another based ondefined connection and communication protocols and APIs. Servicesprovided by HAVi's distributed application system include an addressingscheme and message transfer, lookup for discovering resources, postingand receiving local or remote events, and streaming and controllingisochronous data streams.

“HomePlug” stands for The HomePlug Powerline Alliance. HomePlug is anot-for-profit corporation formed to provide a forum for the creation ofopen specifications for high speed home powerline networking productsand services. The HomePlug specification is designed for delivery ofInternet communications and multimedia to homes through the home poweroutlet using powerline networking standards.

The HomePlug protocol allows HomePlug-enabled devices to communicateacross powerlines using Radio Frequency signals (RF). The HomPlugprotocol uses Orthogonal Frequency Division Multiplexing (OFDM) to splitthe RF signal into multiple smaller sub-signals that are thentransmitted from one HomPlug enabled-device to another HomePlug-enableddevice at different frequencies across the powerline.

“HTTP” stands for ‘HyperText Transport Protocol,’ the standard datacommunications protocol of the World Wide Web.

“ID” abbreviates “identification” as used by convention in thisspecification with nouns represented in data elements, so that ‘user ID’refers to a user identification and ‘userID’ is the name of a dataelement in which is stored a user identification. For a further exampleof the use of ‘ID’: ‘metric ID’ refers to a metric identification and‘metricID’ is the name of a data element in which is stored a metricidentification.

“IEEE 1394” is an external bus standard that supports data transferrates of up to 400 Mbps (400 million bits per second). Apple, whichoriginally developed IEEE 1394, uses the trademarked name “FireWire.”Other companies use other names, such as i.link and Lynx, to describetheir 1394 products.

A single 1394 port can be used to connect up to 63 external devices. Inaddition to high speed, 1394 also supports isochronous datatransfer—delivering data at a guaranteed rate. This makes it ideal fordevices that need to transfer high levels of data in real-time, such asvideo.

“The Internet” is a global network connecting millions of computersutilizing the ‘internet protocol’ or ‘IP’ as the network layer of theirnetworking protocol stacks. The Internet is decentralized by design.Each computer on the Internet is independent. Operators for eachcomputer on the Internet can choose which Internet services to use andwhich local services to make available to the global Internet community.There are a variety of ways to access the Internet. Many onlineservices, such as AMERICA ONLINE™, offer access to some Internetservices. It is also possible to gain access through a commercialInternet Service Provider (ISP). An “internee” (uncapitalized) is anynetwork using IP as the network layer in its network protocol stack.

“JAR” is an abbreviation for ‘JAVA™ archive.’ JAR is a file format usedto bundle components used by a JAVA™ application. JAR files simplifydownloading applets, because many components (.class files, images,sounds, etc.) can be packaged into a single file. JAR also supports datacompression, which further decreases download times. By convention, JARfiles end with a ‘.jar’ extension.

“JES” stands for JAVA™ Embedded Server. JES is a commercialimplementation of OSGi that provides a framework for development,deployment, and installation of applications and services to embeddeddevices.

“LAN” is an abbreviation for “local area network.” A LAN is a computernetwork that spans a relatively small area. Many LANs are confined to asingle building or group of buildings. However, one LAN can be connectedto other LANs over any distance via telephone lines and radio waves. Asystem of LANs connected in this way is called a wide-area network(WAN). The Internet is an example of a WAN.

“LonWorks” is a networking platform available from Echelon®. Lon Worksis currently used in various network applications such as appliancecontrol and lighting control. The LonWorks networking platform uses aprotocol called “LonTalk” that is embedded within a “Neuron Chip”installed within Lon Works-enabled devices.

The Neuron Chip is a system-on-a-chip with multiple processors,read-write and read-only memory (RAM and ROM), and communication and I/Osubsystems. The read-only memory contains an operating system, theLonTalk protocol, and an I/O function library. The chip has non-volatilememory for configuration data and for application programs, which can bedownloaded over a LonWorks network to the device. The Neuron Chipprovides the first 6 layers of the standard OSI network model. That is,the Neuron Chip provides the physical layer, the data link layer, thenetwork layer, the transport layer, the session layer, and thepresentation layer.

The Neuron Chip does not provide the application layer programming.Applications for LonWorks networks are written in a programming languagecalled “Neuron C.” Applications written in Neuron C are typicallyevent-driven, and therefore, result in reduced traffic on the network.

“OSGI” refers to the Open Services Gateway Initiative, an industryorganization developing specifications for services gateways, includingspecifications for delivery of service bundles, software middlewareproviding compliant data communications and services through servicesgateways. The Open Services Gateway specification is a JAVA™ basedapplication layer framework that gives service providers, networkoperator device makers, and appliance manufacturer's vendor neutralapplication and device layer APIs and functions.

The “OSI Model” or Open System Interconnection, model defines anetworking framework for implementing protocols in seven layers. Controlis passed from one layer to the next, starting at the application layerin one network station, proceeding to the bottom layer, over the channelto the next network station and back up the hierarchy.

“SMF” stands for “Service Management Framework™” available from IBM®.SMF is a commercial implementation of OSGi for management of networkdelivered applications on services gateways.

“USB” is an abbreviation for “universal serial bus.” USB is an externalbus standard that supports data transfer rates of 12 Mbps. A single USBport can be used to connect up to 127 peripheral devices, such as mice,modems, and keyboards. USB also supports Plug-and-Play installation andhot plugging.

“WAP” refers to the Wireless Application Protocol, a protocol for usewith handheld wireless devices. Examples of wireless devices useful withWAP include mobile phones, pagers, two-way radios, and hand-heldcomputers. WAP supports many wireless networks, and WAP is supported bymany operating systems. Operating systems specifically engineered forhandheld devices include PalmOS, EPOC, Windows CE, FLEXOS, OS/9, andJavaOS. WAP devices that use displays and access the Internet run“microbrowsers.” The microbrowsers use small file sizes that canaccommodate the low memory constraints of handheld devices and thelow-bandwidth constraints of wireless networks.

The “X-10” means the X-10 protocol. Typical X-10 enabled devicescommunicate across AC powerline wiring, such as existing AC wiring in ahome, using an X-10 transmitter and an X-10 receiver. The X-10transmitter and the X-10 receiver use Radio Frequency (RF) signals toexchange digital information. The X-10 transmitter and the X-10 receivercommunicate with short RF bursts which represent digital information. ABinary 1 is represented by a 1 millisecond burst of 120 KHz. and aBinary 0 by the absence of 120 KHz burst followed by the presence of aburst.

In the X-10 protocol, data is sent in data strings called frames. Theframe begins with a 4 bit start code designated as “1110.” Following thestart code, the frame identifies a particular domain, such as house,with a 4 bit “house code,” and identifies a device within that domainwith a 4 bit “devices code.” The frame also includes a command string of8 bits identifying a particular preset command such as “on,” “off,”“dim,” “bright,” “status on,” “status off,” and “status request.”

Exemplary Architecture

FIG. 1 is a block diagram of exemplary architecture useful inimplementing methods of administering devices in accordance withembodiments of the present invention. The architecture of FIG. 1includes a domain (118). The term “domain” in this specification means aparticular networked environment. Examples of various domains includehome networks, car networks, office network, and others as will occur tothose of skill in the art.

The domain (118) of FIG. 1 includes a services gateway (106). A servicesgateway (106) is, in some exemplary architectures, an OSGi compatibleservices gateway (106). While exemplary embodiments of methods foradministering devices are described in this specification using OSGi,many other applications and frameworks, will work to implement themethods of administering devices according to the present invention, andare therefore also well within the scope of the present invention.Commercial implementations of OSGi, such as JES and SMF, are also usefulin implementing methods for administering devices.

In the exemplary architecture of FIG. 1, the services gateway (126)includes a services framework (126). The services framework (126) ofFIG. 1 is a hosting platform for running ‘services.’ Services are themain building blocks for creating applications in the OSGi. An OSGiservices framework (126) is written in JAVA™ and therefore, typicallyruns on a JAVA™ Virtual Machine (JVM) (150).

The exemplary architecture of FIG. 1 includes a DML (108). “DML” (108)is an abbreviation for Domain Mediation Layer. In many embodiments ofthe architecture of FIG. 1, the DML (108) is application software usefulin implementing methods of administering devices in accordance with thepresent invention. In some embodiments of the present invention, the DMLis OSGi compliant application software, and is therefore implemented asa service or a group of services packaged as a bundle installed on theservices framework (126). In this specification, DMLs are oftendiscussed in the context of OSGi. However, the discussion of OSGI is forexplanation and not for limitation. In fact, DMLs according to variousembodiments of the present invention can be implemented in anyprogramming language, C, C++, COBOL, FORTRAN, BASIC, and so on, as willoccur to those of skill in the art, and DMLs developed in languagesother than JAVA™ are installed directly upon an operating system oroperating environment rather than a JVM.

In the exemplary architecture of FIG. 1, the services gateway (106) iscoupled for data communications with a metric sensor (406). A metricsensor (406) is a device that reads an indication of a user's condition,and creates a user metric in response to the indication of the user'scondition. An “indication of a user's condition” is a quantifiableaspect of a user's condition and a quantity measuring the aspect. Forexample, a quantifiable aspect of a user's condition is a bodytemperature of 99.2 degrees Fahrenheit. Examples of quantifiable aspectsof a user's condition include body temperature, heart rate, bloodpressure, location, galvanic skin response, and others as will occur tothose of skill in the art.

A “user metric” is a data structure representing an indication of usercondition. In many examples of methods for administering devices inaccordance with the present invention, a user metric is implemented as adata structure, class, or object that includes a userID field, ametricID field, and a metric value field. A typical userID fieldidentifies the user whose indication of condition is represented by themetric. A typical metricID field identifies the quantifiable aspect ofuser condition the metric represents, such as, for example, bloodpressure, heart rate, location, or galvanic skin response. A typicalmetric value field stores a quantity measuring the aspect of a user'scondition.

Wearable and wireless heart rate monitors, galvanic skin responsemonitors, eye response monitors, and breathing monitors useful as oreasily adaptable for use as metric sensors are currently available fromQuibit Systems, Inc. The ‘Polar’ series of heart rate monitors from BodyTrends, Inc., and the magnetoelastic gastric pH sensors from SentecCorporation are other examples of readily available biomedical sensorsuseful as or easily adaptable for use as metric sensors.

In order for a conventional sensor, such as a biomedical sensor, to beuseful as a metric sensor that transmits multiple metric types in adomain containing multiple users, the sensor advantageously transmitsnot only a value of the each aspect it measures, but also transmits auser ID and a metricID. The user ID is useful because typicalembodiments of the present invention include a DML capable ofadministering devices on behalf of many users simultaneously. ThemetricID is useful because a single user may employ more than one metricsensor at the same time or employ a metric sensor capable of monitoringand transmitting data regarding more than one aspect of user condition.All wireless sensors at least transmit a metric value according to somewireless data communications protocol. To the extent that any particularsensor ‘off-the-shelf’ does not also transmit user ID or metricID, sucha sensor is easily adapted, merely by small modifications of itscontrolling software, also to include in its transmissions user IDs andmetricID.

Although it is expected that most DMLs will support metric IDs and userIDs, it is possible, under some circumstances within the scope of thepresent invention, to use an off-the-shelf sensor as a metric sensoreven if the sensor does not provide metric ID and user ID in its outputtelemetry. Consider an example in which only a single person inhabits adomain having device controlled or administered by a DML tracking only asingle metric, such as, for example, heart rate. A DML tracking only onemetric for only one user could function without requiring a metric typecode in telemetry received from the metric sensor because, of course,only one type of metric is received. In this example, strictly speaking,it would be possible for an off-the-shelf, Bluetooth-enabled heart ratesensor, such as a ‘Polar’ sensor from Body Trends, to function as ametric sensor. This example is presented only for explanation, becauseas a practical matter it is expected that most DMLs according toembodiments of the present invention will usefully and advantageouslyadminister more than one type of metric (therefore needing a metric IDcode in their telemetry) on behalf of more than one user (thereforeneeding a user ID in their telemetry).

In many embodiments of the present invention, the metric sensor isadvantageously wirelessly coupled for data communications with theservices gateway (106). In many alternative embodiments, the metricsensor transmits the user metric to the DML through a services gatewayusing various protocols such as Bluetooth, 802.11, HTTP, WAP, or anyother protocol that will occur to those of skill in the art.

In the exemplary architecture of FIG. 1, the domain (118) includes adevice (316) coupled for data communications with the services gateway(106) across a LAN (105). In many embodiments of the present invention,a domain (118) will include many devices. A home domain, for example,may include a home network having a television, numerous lights, arefrigerator, a freezer, a coffee pot, a dishwasher, a dryer, a CDplayer, a DVD player, a personal video recorder, or any othernetworkable device that will occur to those of skill in the art. Forease of explanation, the exemplary architecture of FIG. 1 illustratesonly three devices (316), but the use of any number of devices is wellwithin the scope of the present invention.

To administer the device (316), the DML must have the device class forthe device containing accessor methods that get and set attributes onthe device, and in some cases, a communication class that provides theprotocols needed to communicate with the device. In some examples of thearchitecture of FIG. 1, a DML has pre-installed upon it, device classesand communications classes for many devices that the DML supports.

To the extent the DML does not have a preinstalled device class andcommunications class for a particular device, the DML can obtain thedevice class and communications class in a number of ways. One way theDML obtains the device class and communications class for the device isby reading the device class and the communications class from thedevice. This requires the device have enough installed memory to storethe device class and communications class. The DML can also obtain thedevice class and communications class from devices that do not containthe device class or communications class installed upon them. One waythe DML obtains the device class and communications class is by readinga device ID from the device, searching the Internet for the device classand communications class, and downloading them. Another way the DMLobtains the device class and communications class is by reading anetwork location from the device downloading, from the network location,the device class and communications class. Three ways have beendescribed for obtaining the device classes and communications classesneeded to administer devices in accordance with the present invention.Other methods will also occur to those of skill in the art.

The exemplary architecture of FIG. 1 includes a non-domain entity (102)that is coupled for data communications with the services gateway (106)across a WAN (104). A “non-domain entity” is any computing device ornetwork location coupled for data communications to the domain but notwithin the domain. The phrase “non-domain entity” is broad and itsinclusion in the architecture of FIG. 1 acknowledges that in manyembodiments of architecture useful in implementing methods ofadministering devices in accordance with the present invention, a givendomain is coupled for data communications with outside non-domainentities.

An example of a non-domain entity is a web server (outside the domain)of a manufacturer of the device (316) installed within the domain. Themanufacturer may operate a website that makes available for downloaddrivers for the device, updates for the device, or any other informationor software for the device. Drivers, updates, information or softwarefor the device are downloadable to the device across a WAN and throughthe services gateway.

FIG. 2 is a block diagram of an exemplary services gateway (106) usefulin implementing methods of administering devices according to thepresent invention. The services gateway (106) of FIG. 2 is, in someexemplary architectures useful in embodiments of the present invention,an OSGi compatible services gateway (106). While exemplary embodimentsof methods for administering a device are described in thisspecification using OSGi, many other applications and frameworks otherthan OSGi will work to implement methods of administering devicesaccording to the present invention and are therefore well within thescope of the present invention. Commercial implementations of OSGi, suchas JES and SMF, are also useful in implementing methods of the presentinvention.

OSGi Stands for ‘Open Services Gateway Initiative.’ The OSGispecification is a JAVA™-based application layer framework that providesvendor neutral application and device layer APIs and functions forvarious devices using arbitrary communication protocols operating innetworks in homes, cars, and other environments. OSGi works with avariety of networking technologies like Ethernet, Bluetooth, the ‘Home,Audio and Video Interoperability standard’ (HAVi), IEEE 1394, UniversalSerial Bus (USB), WAP, X-10, Lon Works, HomePlug and various othernetworking technologies. The OSGi specification is available for freedownload from the OSGi website at www.osgi.org.

The services gateway (130) of FIG. 2 includes a service framework (126).In many example embodiments the service framework is an OSGi serviceframework (126). An OSGi service framework (126) is written in JAVA™ andtherefore, typically runs on a JAVA™ Virtual Machine (JVM). In OSGi, theservice framework (126) of FIG. 1 is a hosting platform for running‘services’ (124). The term ‘service’ or ‘services’ in this disclosure,depending on context, generally refers to OSGi-compliant services.

Services (124) are the main building blocks for creating applicationsaccording to the OSGi. A service (124) is a group of JAVA™ classes andinterfaces that implement a certain feature. The OSGi specificationprovides a number of standard services. For example, OSGi provides astandard HTTP service that creates a web server that can respond torequests from HTTP clients.

OSGi also provides a set of standard services called the Device AccessSpecification. The Device Access Specification (“DAS”) provides servicesto identify a device connected to the services gateway, search for adriver for that device, and install the driver for the device.

Services (124) in OSGi are packaged in ‘bundles’ (121) with other files,images, and resources that the services (124) need for execution. Abundle (121) is a JAVA™ archive or ‘JAR’ file including one or moreservice implementations (124), an activator class (127), and a manifestfile (125). An activator class (127) is a JAVA™ class that the serviceframework (126) uses to start and stop a bundle. A manifest file (125)is a standard text file that describes the contents of the bundle (121).

In the exemplary architecture of FIG. 2 includes a DML (108). In manyembodiments of the present invention, the DML is an OSGi service thatcarries out methods of administering devices. The DML (108) of FIG. 2 ispackaged within a bundle (121) and installed on the services framework(126).

The services framework (126) in OSGi also includes a service registry(128). The service registry (128) includes a service registration (129)including the service's name and an instance of a class that implementsthe service for each bundle (121) installed on the framework (126) andregistered with the service registry (128). A bundle (121) may requestservices that are not included in the bundle (121), but are registeredon the framework service registry (128). To find a service, a bundle(121) performs a query on the framework's service registry (128).

Exemplary Classes and Class Cooperation

FIG. 3 is a block diagram illustrating exemplary classes useful inimplementing methods for administering devices in accordance with thepresent invention. A “class” is a complex data structure that typicallyincludes member methods, functions, or software routines as well as dataelements. Instances of classes are referred to as “objects” or “classobjects.” A “method” or “member method” is a process performed by anobject. The exemplary classes of FIG. 3 are presented as an aid tounderstanding of the present invention, not for limitation. Whilemethods of administering devices in accordance with the presentinvention are discussed generally in this specification in terms ofJAVA™, JAVA™ is used only for explanation, not for limitation. In fact,methods of administering devices in accordance with the presentinvention can be implemented in many programming languages includingC++, Smalltalk, C, Pascal, Basic, COBOL, Fortran, and so on, as willoccur to those of skill in the art.

The class diagram of FIG. 3 includes an exemplary DML class (202). Aninstance of the exemplary DML class (202) of FIG. 3 provides membermethods that carry out the steps useful in administering devices inaccordance with the present invention. The exemplary DML class of FIG. 3is shown with an Activator.start( ) method so that the DML can bestarted as a service in an OSGi framework. Although only one membermethod is shown for this DML, DMLs in fact will often have more membermethods as needed for a particular embodiment. The DML class of FIG. 3also includes member data elements for storing references to servicesclasses, often created by the DML's constructor. In this example, theDML provides storage fields for references to a metric service (552), ametric range service (558), a communication service (554), an actionservice (560), a device service (556), a metric vector service (559) anda metric space service (561), and dynamic action list service (563).

The metric service class (204) of FIG. 3 provides member methods thatreceive user metrics from a DML and create, in response to receiving theuser metrics from the DML, an instance of a metric class. The metricservice class (204) of FIG. 3 includes a createMetric (UserID, MetricID,MetricValue) member method (562). The createMetric( ) member method is,in some embodiments, a factory method parameterized with a metric IDthat creates and returns a metric object in dependence upon the metricID. In response to getting a user metric from the DML, the exemplaryinstance of the metric service class (204) of FIG. 3 creates an instanceof a metric class and returns to the DML a reference to the new metricobject.

Strictly speaking, there is nothing in the limitations of the presentinvention that requires the DML to create metric object through afactory method. The DML can for example proceed as illustrated in thefollowing pseudocode segment:

// receive on an input stream a metric message // extract from themetric message a userID, // a metric ID, and a metric value, so that:int userID = // userID from the metric message int metricID = //metricID from the metric message int metricValue = // metric value fromthe metric message Metric aMetric = new Metric( ); aMetric.setUserID(userID); aMetric.setMetricID(metricID);aMetric.setMetricValue(metricValue); aMetric.start ( );

This example creates a metric object and uses accessor methods to loadits member data. This approach provides exactly the same class of metricobject for each metric, however, and there are circumstances whenmetrics advantageously utilize different concrete class structures. Inthe case of metrics for heart rate and blood pressure, for example, bothmetric values may be encoded as integers, where a metric value for polarcoordinates on the surface of the earth from a GPS transceiver, forexample, may advantageously be encoded in a more complex data structure,even having its own Location class, for example. Using a factory methodeases the use of more than one metric class. A DML using a factorymethod to create metric objects can proceed as illustrated in thefollowing exemplary pseudocode segment:

// receive on an input stream a metric message // extract from themetric message a userID, // a metric ID, and a metric value, so that:int userID = // userID from the metric message int metricID = //metricID from the metric message int metricValue = // metric value fromthe metric message Metric aMetric =MetricService.createMetricObject(userID, metricID,   metricValue);aMetric.start( );

This example relies on the factory method createMetric( ) to set theparameter values into the new metric object. A metric service and afactory method for metric object can be implemented as illustrated inthe following pseudocode segment:

// // Metric Service Class // class MetricService {  public staticMetric createMetricObject(userID, metricID, metricValue)  {   MetricaMetric;   switch(metricID)   {    case 1: aMetric = newHeartRateMetric(userID, metricID,    metricValue);      break;    case2: aMetric =      new BloodPressureMetric(userID, metricID,metricValue);      break;    case 3: aMetric = new GPSMetric(userID,metricID metricValue);      break;    } // end switch( )    returnaMetric;  } // end createMetric( ) } // end class MetricService

MetricService in this example implements a so-called parameterizedfactory design pattern, including a factory method. In this example, thefactory method is a member method named ‘createMetricObject().’CreateMetricObject( ) accepts three parameters, a user ID, a metricID, and a metric value. CreateMetricObject( ) implements a switchstatement in dependence upon the metric ID to select and instantiate aparticular concrete metric class. The concrete metric classes in thisexample are HeartRateMetric, BloodPressureMetric, and GPSMetric, each ofwhich extends a Metric base class. CreateMetricObject( ) returns to thecalling DML a reference to a new metric object. The call from the DML:

Metric aMetric=MetricService.createMetricObject(userID, metricID,metricvalue);

is polymorphic, utilizing a reference to the base class Metric, so thatthe calling DML neither knows nor cares which class of metric object isactually instantiated and returned. The following is an example ofextending a Metric base class to define a concrete metric classrepresenting a user's location on the surface of the earth extending aMetric base class:

Class GPSMetric extends Metric {   int myUserID;   int myMetricID  class GPSLocation {     Latitude myLatitude;     LongitudemyLongitude;   }   Class Latitude {     String direction;     intdegrees;     int minutes;     int seconds;   }   Class Longitude {    String direction;     int degrees;     int minutes;     int seconds;  }   GPSLocation myLocation;   GPSMetric(int userID, int metricIDGPSLocation metricValue) {     myUserID = userID;     myMetricID =metricID:     myLocation = metricValue;   } }

The example concrete class GPSMetric provides storage for latitude andlongitude. GPSMetric provides a constructor GPSMetric( ) that takesinteger arguments to set userID and metricID but expects its metricValueargument to be a reference to a GPSLocation object, which in turnprovides member data storage for latitude and longitude.

The class diagram of FIG. 3 includes an exemplary metric class (206).The exemplary metric class (206) of FIG. 3 represents a user metric. Auser metric comprises data describing an indication of user condition.An indication of a user's condition is a quantifiable aspect of a user'scondition and a quantity measuring the aspect. Examples of quantifiableaspects of a user's condition include body temperature, heart rate,blood pressure, location, galvanic skin response, or any other aspect ofuser condition as will occur to those of skill in the art.

The exemplary metric class (206) of FIG. 3 includes a user ID field(486), a metric ID field (488), a value field (490). The user ID field(486) identifies the user. The metric ID (488) field identifies the usermetric that an instance of the metric class represents. That is, thekind of user metric. The value field (490) includes a value of the usermetric.

The exemplary metric class of FIG. 3 also includes data storage for ametric action list (622). A metric action list is a data structurecontaining action IDs identifying actions that when executed administerdevices in a manner that affect the same aspect of user conditionrepresented by the metric. A metric for body temperature, for example,may have an associated metric action list including an action ID thatwhen executed results in turning on a ceiling fan. In many examples ofmethods for administering devices, the action IDs in the metric actionlists are used to identify action IDs for inclusion in a dynamic actionlist.

This exemplary metric class (206) is an example of a class that can invarious embodiments be used in various embodiments as a generic class,instances of which can be used to store or represent more than one typeof metric having identical or similar member data elements as discussedabove. Alternatively in other embodiments, a class such as this examplemetric class (206) can be used as a base class to be extended byconcrete derived classes each of which can have widely disparate memberdata type, also described above.

The class diagram of FIG. 3 includes a metric vector service (207). Themetric vector service class (207) of FIG. 3 provides member methods thatcreate, in response to receiving the user metrics from the metricservice, an instance of a metric vector class. In many exampleembodiments, the createMetric vectorObject( ) member method (565)identifies from a metric vector list a metric vector ID for the usermetric vector in dependence upon the user ID, and the metric ID. Ifthere is not a metric vector for the user and for that metric ID in themetric vector service's metric vector list, the metric vector serviceinstantiates one and stores its metric vector ID in a metric vectortable, indexed by the associated user ID and metric ID. Creating ametric vector object can be implemented as illustrated in the followingpseudocode segment:

// receive a metric on input stream // extract its userID as an integer// instantiate a metric object Metric newMetric =metricService.createMetricObject(metricID); int MetricVectorID = 0;if((MetricVectorID = MetricVectorList.get(userID, metricID)) == null) {  MetricVector newMetricVector =  MetricVectorService.createMetricVectorObject(userID, metricID);  MetricVectorID = newMetricVector.MetricVectorID;  MetricVectorList.add(MetricVectorID, newMetricVector) }

In the pseudocode example above, if the metric vector service receives ametric having a userID for which it has no metric vector identified inthe metric vector service's metric vector table, the metric vectorservice creates a new metric vector having a new metric vector ID forthe user and adds the metric vector to the metric vector list.

The class diagram of FIG. 3 includes a metric vector class (606).Objects of the metric vector class represent a complex indication ofuser condition. A user metric vector typically includes a collection ofa user metrics each representing a single quantifiable aspect of auser's condition and a quantity measuring the aspect. A user metricvector comprised of a plurality of disparate user metrics thereforerepresents a complex indication of user condition having multiplequantifiable aspects of a user's condition and multiple quantitiesmeasuring the aspects. The metric vector class (606) includes dataelements for storing a user ID (486) identifying the user and a metriclist (652) for storing references to a plurality of disparate metricobjects.

The exemplary metric vector (606) of FIG. 3 also includes data storagefor a dynamic action list (626). A dynamic action list is a list ofaction IDs created in dependence upon metric action lists that areassociated with the particular metrics of the user metric vector thatare outside their corresponding metric ranges of the user metric space.That is, each metric of the metric vector that is outside itscorresponding metric range has an associated metric action list. Adynamic action list includes action IDs identified in dependence uponthose metric action lists associated with the particular metrics of auser metric vector outside their corresponding metric ranges of the usermetric space. A dynamic action list advantageously provides a list ofaction IDs tailored to the user's current condition.

Objects of the exemplary metric vector class also typically includemember methods for determining if the metric vector is outside a usermetric space. This exemplary metric vector class is an example of aclass that can in various embodiments be used as a generic class,instances of which can be used to store or represent more than one typeof vector having identical or similar member data elements.Alternatively in other embodiments, a class such as this example metricvector class can be used as a base class to be extended by concretederived classes each of which can have disparate member data types.

The class diagram of FIG. 3 includes metric range service class (208).The metric range service class (208) provides member methods thatinstantiate an instance of a metric range class. The metric rangeservice class (208) of FIG. 3 includes a createRangeObject(UserID,MetricID) member method (572). The createRangeObject( ) member method isa factory method parameterized with a userID and a metric ID thatcreates a metric range object in dependence upon the userID and metricID. The createRangeObject( ) factory method returns a reference to themetric range object to the metric object. The createRangeObject( ) is aparameterized factory method that can be implemented using the samedesign patterns outlined by the exemplary psuedocode provided in thedescription of the createMetricObject( ) factory method.

The class diagram of FIG. 3 includes an exemplary metric range class(210). An instance of the exemplary metric range class represents apredefined metric range for a user for a metric. A maximum value andminimum value in a metric range object are compared with a metric valueto determine whether the metric value of the metric object is outside apredefined metric range. The exemplary metric range class (210) of FIG.3 includes range ID field (463) identifying the metric range, and ametric ID field (462) identifying the user metric. The exemplary metricrange class (210) of FIG. 3 includes a user ID field (464) identifyingthe user. The metric range class also includes a Max field (468) and aMin field (470) containing a maximum value and a minimum value defininga metric range.

The exemplary metric range class (210) of FIG. 3 is an example of aso-called data object, that is, a class that serves only as a containerfor data, with little or no processing done on that data by the membermethods of the class. In this example, objects of the metric range classare used primarily to transfer among other objects the minimum andmaximum values of a metric range. The metric range class of FIG. 3includes a default constructor (not shown), but strictly speaking, wouldneed no other member methods. If the metric range class were providedwith no other member methods, cooperating object could access its memberdata elements directly by coding, such as, for example:“someMetricRange.max” or “someMetricRange.min.” The particular examplein this case (210), however, is illustrated as containing accessormethods (471, 473) for the minimum and maximum values of its range, apractice not required by the invention, but consistent with programmingin the object oriented paradigm.

The class diagram of FIG. 3 includes a metric space service class (209).The metric space service class (209) includes a member methodcreateMetricSpace( ) that searches a metric space list, or other datastructure, to identify a metric space for a user. If no such metricspace exists, createMetricSpace( ) instantiates one and stores themetric space ID in the metric space list. Creating a metric space objectcan be implemented by way of the following exemplary psuedocode:

// extract its userID and MetricVector ID as an integer // instantiate ametric space object MetricVector newMetricVector  =MetricVectorService.createMetricVectorObject(userID,  MetricVectorID); if((spaceID = MetricSpaceList.get(userID,metricvectorID)) == null) { MetricSpace newMetricSpace =  MetricSpaceService.createMetricSpace(userID, MetricVectorID);MetricSpaceID = newMetricSpace.SpaceID; MetricSpaceList.add(SpaceID,newMetricSpace) }

In the pseudo code example above, the metric space service searches ametric space list for a metric space. If the list contains no metricspace for the userID and metric vector ID, thenMetricSpaceService.createMetricSpace(userID, MetricVectorID) creates anew metric space with a new metric space ID.

The class diagram of FIG. 3 includes a metric space class. The usermetric space is comprised of a plurality of user metric ranges fordisparate metrics. The exemplary metric space includes data elements forstoring a user ID (405) identifying the user and a space ID (908)identifying the metric space. The metric space (610) of FIG. 3 alsoincludes data storage (655) for a list of references to disparate metricranges for a user. The disparate metric ranges of the metric spacecorrespond in kind to the metrics in the user metric vector. That is, intypical embodiments, the user metric vector includes a set of disparatecurrent metrics and the user metric space includes a set ofcorresponding metric ranges for the user.

The class diagram of FIG. 3 includes an action service class (217). Theaction service class includes member methods that instantiate a metricaction list for a metric, instantiate action objects store references tothe action objects in the action list, and return to a calling metric areference to the action list, all of which can be implemented asillustrated by the following exemplary pseudocode ActionService class:

// // Action Service Class // class ActionService {  public staticAction createActionList(userID, MetricID)  {   ActionList anActionList =new ActionList( );   int actionID;   // with finds of database actionrecords storing data describing actions   for(/* each action recordmatching userID and metricID */) {    // obtain action ID from eachmatching action record    actionID = // action ID from matching databaserecord    // * the action constructors below obtain from a device    //service a list of devices administered by the action object   switch(actionID)    {     case 1: Action anAction1 = newAction1(DeviceService,     actionID);       anActionList.add(anAction1);      break;     case 2: Action anAction2 = new Action2(DeviceService,    actionID);       anActionList.add(anAction2);       break;     case3: Action anAction3 = new Action3(DeviceService,     actionID);      anActionList.add(anAction3);       break;     case 4: ActionanAction4 = new Action4(DeviceService,     actionID);      anActionList.add(anAction4);       break;     case 5: ActionanAction5 = new Action5(DeviceService,     actionID);      anActionList.add(anAction5);       break;    } // end switch( )  } // end for( )   return anActionList;  } // endcreateActionListObject( ) } // end class ActionService

The createActionList( ) method in ActionService class instantiates ametric action list for a user metric with “ActionList anActionList=newActionList( ).” CreateActionList( ) then searches an action record tablein a database for records having user IDs and metric IDs matching itscall parameters. For each matching record in the table,createActionList( ) instantiates an action object through its switchstatement. The switch statement selects a particular concrete derivedaction class for each action ID retrieved from the action record table.CreateActionList( ) stores a references to each action object in theaction list with “anActionList.add( ).” CreateActionList( ) returns areference to the action list with “return anActionList.”

The class diagram of FIG. 3 includes an exemplary action class (216). Aninstance of the action class represents an action that when executedresults in the administration of a device. The exemplary action class ofFIG. 3 includes an action ID field (450). The doAction( ) method (456)in the exemplary action class (216) is programmed to obtain a devicelist (458) from, for example, a call to DeviceService.createDeviceList(). Action.doAction( ) (456) typically then also is programmed to callinterface methods in each device in its device list to carry out thedevice controlling action.

The action object (216) also includes a member methodcreateDeviceEffRecord( ) (457). createDeviceEffRecord( ) creates adevice effectiveness record when the action object is executed. A deviceeffectiveness record is a data structure including information used toevaluate whether the administration of a particular device administeredby executing a particular action was effective in affecting a particularuser's condition. Device effectiveness records are discussed below withreference to the method of FIG. 12.

The class diagram of FIG. 3 includes a dynamic action list service. Thedynamic action list service of FIG. 3 includes a member methodcreateDynamicList( ) (569). In many embodiments, createDynamicList iscalled by member methods within a user metric vector and parameterizedwith action IDs retrieved from metric action lists associated with theparticular metrics that are outside their corresponding metric ranges.CreateDynamicList creates a dynamic action list in dependence upon themetric action lists and returns to its caller a reference to the dynamicaction list.

The class diagram of FIG. 3 includes a device service class (218). Thedevice service class provides a factory method namedcreateDeviceList(actionID) that creates a list of devices and returns areference to the list. In this example, createDeviceList( ) operates ina fashion similar to ActionService.createActionList( ) described above,by instanting a device list, searching through a device table for deviceIDs from device records having matching action ID entries, instantiatinga device object of a concrete derived device class for each, adding tothe device list a reference to each new device object, and returning toa calling action object a reference to the device list. In this example,however, the factory method createDeviceList( ) not only retrieves adevice ID from its supporting data table, but also retrieves a networkaddress or communications location for the physical device to becontrolled by each device object instantiated, as illustrated by thefollowing exemplary pseudocode:

// // Device Service Class // class DeviceService {  public staticDevice createDeviceList(actionID)  {   DeviceList aDeviceList = newDeviceList( );   int deviceID;   // with finds of database devicerecords storing data describing   devices   for(/* each device recordmatching actionID */) {    // obtain device ID and device address fromeach matching device    record    deviceID = // device ID from matchingdatabase record    deviceAddress = // device ID from matching databaserecord    // reminder: the device constructors below obtain from adevice    // service a list of devices administered by the device object   switch(deviceID)    {     case 1: Device aDevice = newDevice1(CommsService,        deviceAddress, deviceID);        break;    case 2: Device aDevice = new Device2(CommsService       deviceAddress, deviceID);        break;     case 3: DeviceaDevice = new Device3(CommsService        deviceAddress, deviceID);       break;     case 4: Device aDevice = new Device4(CommsService       deviceAddress, deviceID);        break;     case 5: DeviceaDevice = new Device5(CommsService        deviceAddress, deviceID);       break;     } // end switch( )     aDeviceList.add(aDevice);   }// end for( )   return aDeviceList;  } // end createDeviceListObject( )} // end class DeviceService

The createDeviceList( ) method in DeviceService class instantiates adevice list for a metric with “DeviceList aDeviceList=new DeviceList().” CreateDeviceList( ) then searches a device record table in adatabase for records having action IDs matching its call parameter. Foreach matching record in the table, createDeviceList( ) instantiates adevice object through its switch statement, passing three parameters,CommsService, deviceAddress, and deviceID. CommsService is a referenceto a communications service from which a device object can obtain areference to a communications object for use in communicating with thephysical device controlled by a device object. DeviceAddress is thenetwork address, obtained from the device table as described above, ofthe physical device to be controlled by a particular device object. Theswitch statement selects a particular concrete derived device class foreach device ID retrieved from the device table. CreateDeviceList( )stores references to each device object in the device list with“aDeviceList.add( ).” CreateDeviceList( ) returns a reference to thedevice list with “return aDeviceList.”

The class diagram of FIG. 3 includes an exemplary device class (214).The exemplary device class (214) of FIG. 3 includes a deviceID field(472) uniquely identifying the physical device to be administered by theexecution of the action. The exemplary device class (214) of FIG. 3includes an address field (480) identifying a location of a physicaldevice on a data communications network. The exemplary device class(214) of FIG. 3 provides a communications field (478) for a reference toan instance of a communications class that implements a datacommunications protocol to effect communications between an instance ofa device class and a physical device.

The device class of FIG. 3 includes an attribute field (481) containinga value of current attribute of the device. An example of a currentattribute of a device is an indication that the device is “on” or “off.”Other examples of current attributes include values indicating aparticular setting of a device. The device class of FIG. 3 also includesaccessor methods (474, 476) for getting and setting attributes of aphysical device. While the exemplary device class of FIG. 3 includesonly one attribute field and accessor methods for getting and settingthat attribute, many device classes useful in implementing methods ofthe present invention can support more than one attribute. Such classescan also include an attribute ID field and accessor methods for gettingand setting each attribute the device class supports.

The exemplary class diagram of FIG. 3 includes a communications serviceclass (219). The communications service class (219) provides a factorymethod named createCommsObject (deviceID, networkAddress) (574) thatinstantiates a communications object that implements a datacommunications protocol to effect communications between an instance ofa device class and a physical device. The createCommsObject( ) method(574) finds a communications class ID in a communications class recordin a communication class table having a device ID that matches its callparameter. In many embodiments, the createCommsObject( ) method (574)then instantiates a particular concrete derived communications classidentified through a switch statement as described above, passing to theconstructor the networkAddress from its parameter list, so that the newcommunications object knows the address on the network to which the newobject is to conduct data communications. Each concrete derivedcommunications class is designed to implement data communicationsaccording to a particular data communications protocol, Bluetooth,802.11b, Lonworks, X-10, and so on.

Class diagram of FIG. 3 includes an exemplary communications base class(215). In typical embodiments, at least one concrete communicationsclass is derived from the base class for each data communicationsprotocol to be supported by a particular DML. Each concretecommunications class implements a particular data communicationsprotocol for communications device objects and physical devices. Eachconcrete communications class implements a particular datacommunications protocol by overriding interface methods (482, 484) toimplement actual data communications according to a protocol.

Communications classes allow device classes (214) to operateindependently with respect to specific protocols required forcommunications with various physical devices. For example, one light ina user's home may communicate using the LonWorks protocol, while anotherlight in the user's home may communicate using the X-10 protocol. Bothlights can be controlled by device objects of the same device classusing communications objects of different communications classes, oneimplementing LonWorks, the other implementing X-10. Both device objectscontrol the lights through calls to the same communications classinterface methods, send( ) (482) and receives (484), neither knowing norcaring that in fact their communications objects use differentprotocols.

FIG. 4 is a class relationship diagram illustrating an exemplaryrelationship among the exemplary classes of FIG. 3. In the classrelationship diagram of FIG. 4, the solid arrows representinstantiation. The solid arrow points from the instantiating class tothe instantiated class. In the class relationship diagram of FIG. 4, thedotted arrows represent references. The arrow points from a referencedclass to a class whose objects possesses references to the referencedclass. That is, an object-oriented relation of composition, a “has-a”relationship between classes, is shown by an arrow with a dotted line.

The exemplary class relationship diagram of FIG. 4 includes a DML class(202). A DML object of the DML class (202) instantiates an object of themetric service class (204), an object of the metric vector service class(207), and an object of the metric space service class (209). The DMLobject also instantiates an object of the metric range service class(208) an object of the action service class (217), and an object of thedynamic action list service class (211). The DML object alsoinstantiates an object of the device service class (218) and an objectof the communications service class (219).

When the DML receives a metric (200) from a metric sensor, the DML usesa call such as:

Metric aMetric=MetricService.createMetricObject(userID, metricID,metricValue)

causing the metric service (204) to instantiate an object of the metricclass (206). The metric service passes a reference to metric object(206) to metric vector service object (207). The metric object containsa reference to an object of the action service class (217) and a metricaction list (622).

As shown in the class relationship diagram of FIG. 4, a metric vectorservice (207) instantiates an object of the metric vector class (606).In many embodiments, the metric vector service class receives areference to a metric object and using a parameterized factory method,such as createMetricVectorObject( ), instantiates a metric vectorobject. As shown in the class relationship diagram of FIG. 4, an objectof the metric vector class (606) contains a reference to an object ofthe metric class (206), an object of the metric space service class(209), an object of the metric space class (610), an object of thedynamic action list service class (211) and a dynamic action list (212).

As shown in the class relationship diagram of FIG. 4, a metric spaceservice (209) instantiates an object of the metric space class (610). Inmany example embodiments, a metric space service uses a parameterizedfactory method, such as createMetricSpace( ), to instantiate a metricspace object. The metric space service passes a reference to the metricspace object (610) to the metric vector object. The metric space object(610) contains a reference to objects of the metric range class (210).

As shown in the class relationship diagram of FIG. 4, the metric rangeservice (208) instantiates an object of the metric range class (210). Inmany examples embodiments of the present invention, the metric rangeservice (208) uses a parameterized factory method, such ascreateRangeObject( ), to instantiate the metric range (210). The metricrange service (208) passes to the metric space service (209) a referenceto the metric range (210).

As shown in the class relationship diagram of FIG. 4, a action service(217) instantiates a metric action list (622) and objects of actionclasses (216). The metric action list (622) is instantiated withreferences to each of the instantiated actions (216). Each action (216)is instantiated with a reference to the device service (218). In typicalexamples of methods according to the present invention, the actionservice (217) uses a parameterized factory method, such ascreateActionList( ), to instantiate a metric action list (622) andinstantiate actions (216). The action service (217) passes, to themetric (206), a reference to the metric action list (622).

As shown in FIG. 4, the dynamic action list service (211) instantiates adynamic action list (626) and passes a reference to the dynamic actionlist (626) to calling methods in the metric vector (606). In typicalexamples of methods according to the present invention, the dynamicaction list service (211) uses a method, such ascreateDynamicActionList( ) to instantiate a dynamic action list. In manyembodiments, createDynamicActionList( ) is parameterized with action IDsof metric action lists associated with user metrics that are outsidetheir corresponding metric ranges. The dynamic action list (626)possesses references to objects of the action class (216).

In the example of FIG. 4, the device service (218) instantiates a devicelist of the device list class (222) and instantiates a device object ofthe device class (214). The device list (222) is instantiated with areference to the device object (214). The device object (214) isinstantiated with a reference to the communications service (219). Intypical examples of methods according to the present invention, thedevice service (218) uses a parameterized factory method, such ascreateDeviceList( ), to instantiate a device list (222) and instantiatea device object (216). The device service (218) passes, to the action(216), a reference to the device list (222)

In the example of FIG. 4, the communications service (219) instantiatesa communications object of the communications class (215). In typicalexamples of the methods according to the present invention, thecommunications service (219) uses a parameterized factory method, suchas createCommsObject( ), to instantiate a communications object (215).The communications service (219) passes, to the device object (214), areference to the communications object (215).

Administering Devices in Dependence Upon User Metrics

FIG. 5 is a data flow diagram illustrating an exemplary method foradministering devices. The method of FIG. 5 includes receiving (302) auser metric (206). As mentioned above, a “user metric” comprises datadescribing an indication of user condition. An “indication of a user'scondition” is a quantifiable aspect of a user's condition and a quantitymeasuring the aspect. Examples of quantifiable aspects of a user'scondition include body temperature, heart rate, blood pressure,location, galvanic skin response, or any other aspect of user conditionas will occur to those of skill in the art.

In typical embodiments of the present invention, a user metric isimplemented as a user metric data structure or record (206), such as theexemplary user metric (206) of FIG. 5. The user metric of FIG. 5includes a userID field (405) identifying the user whose indication ofcondition is represented by the metric. The user metric (206) of FIG. 5also includes a metric ID field (407) identifying the aspect of usercondition the metric represents, such as, for example, blood pressure,heart rate, location, or galvanic skin response. The user metric (204)also includes a value field (409) containing the value of the aspect ofthe user's condition that the metric represents. An example of a valueof a metric is a body temperature of 100° Fahrenheit.

In many embodiments of the method of FIG. 5, receiving (302) a usermetric includes receiving a user metric from a metric sensor (406). Insome examples of the method of FIG. 5, the metric sensor (406) reads anindication of a user's condition, creates a user metric in dependenceupon the indication of a user's condition, and transmits the user metricto a DML. In many embodiments, the metric sensor transmits the usermetric to the DML in a predefined data structure, such as the metric(206) of FIG. 5, to the DML using, for example, protocols such asBluetooth, 802.11, HTTP, WAP, or any other protocol that will occur tothose of skill in the art.

In the method of FIG. 5, receiving (302) a user metric includesreceiving a user metric into metric cache memory (305). That is, a usermetric is received by a DML and then stored in cache. In manyembodiments of the method of FIG. 5, metric cache memory (305) is cachememory available to a DML to facilitate carrying out steps ofadministering devices in accordance with the present invention.

The method of FIG. 5 includes determining (306) whether a value of theuser metric is outside of a predefined metric range. A predefined metricrange includes a predetermined range of values for a given metric ID fora particular user. In many embodiments of the method of FIG. 5, thepredefined metric range is designed as a range of typical or normalmetrics values for a user. One example of a predefined metric range is arange of metric values representing a resting heart rate of 65-85 beatsper minute.

In many examples of the method of FIG. 5, a predefined metric range fora user is implemented as a data structure or record such as the metricrange (210) of FIG. 5. The metric range of FIG. 5 includes a metric IDfield (462) identifying the kind of user metrics. The metric range ofFIG. 5 includes a user ID field (464) identifying the user for whom themetric range represents a range of metric values. The metric range ofFIG. 5, for example, includes a Max field (468) representing the maximummetric value of the metric range and a Min field (470) representing theminimum metric value of the metric range. That is, in typicalembodiments, it is a maximum and minimum metric value in a range thatdefines a value range for the metric.

In many embodiments, determining (306) that the value of the user metric(206) is outside a predefined metric range includes comparing the metricvalue of a user metric with the maximum and minimum values from a metricrange for that metric and for the same user. In many examples of themethod of FIG. 5, determining that a user metric is outside a predefinedmetric range also includes determining that the metric value (409) ofthe user metric (206) is either greater than the maximum value (468) ofthe metric range (210) or below the minimum value (470) of the range inthe metric range (210). A user metric of metric ID identifying themetric as ‘heart rate’ having, for example, a metric value of 100 beatsper minute is outside the exemplary metric range for resting heart rateof 65-85 beats per minute.

If the value of the user metric is outside the metric range, the methodof FIG. 5 includes identifying (310) an action in dependence upon theuser metric. An action includes one or more computer programs,subroutines, or member methods that when executed, control one or moredevices. Actions are typically implemented as object oriented classesand manipulated as objects or references to objects. In fact, in thisspecification, unless context indicates otherwise, the terms ‘action,’‘action object,’ and ‘reference to an action object’ are treated more orless as synonyms. In many embodiments of the method of FIG. 5, an actionobject calls member methods in a device class to affect currentattributes of the physical device. In many embodiments of the method ofFIG. 5, action classes or action objects are deployed in OSGi bundles toa DML on a services gateway.

In the method of FIG. 5, identifying (310) an action includes retrieving(365) an action ID (315) from a metric action list (622) organized byuser ID and metric ID. In the method of FIG. 5, retrieving an action IDfrom a metric action list includes retrieving from a list theidentification of the action (the ‘action ID’) to be executed when avalue of a metric of a particular metric ID and for a particular user isoutside the user's predetermined metric range. The action list can beimplemented, for example, as a JAVA™ list container, as a table inrandom access memory, as a SQL database table with storage on a harddrive or CD ROM, and in other ways as will occur to those of skill inthe art.

As mentioned above, the actions themselves comprise software, and so canbe implemented as concrete action classes embodied, for example, in aJAVA™ package imported into the DML at compile time and therefore alwaysavailable during DML run time. Executing (314) an action (312) thereforeis often carried out in such embodiments by use of a switch( ) statementin the DML. Such a switch( )statement can be operated in dependence uponthe action ID and implemented, for example, as illustrated by thefollowing segment of pseudocode:

switch (actionID) {   Case 1: actionNumber1.take_action( ); break;  Case 2: actionNumber2.take_action( ); break;   Case 3:actionNumber3.take_action( ); break;   Case 4:actionNumber4.take_action( ); break;   Case 5:actionNumber5.take_action( ); break;   // and so on } // end switch( )

The exemplary switch statement selects a particular device controllingobject for execution depending on the action ID. The device controllingobjects administered by the switch( ) in this example are concreteaction classes named actionNumber1, actionNumber2, and so on, eachhaving an executable member method named ‘take_action( ),’ which carriesout the actual work implemented by each action class.

Executing (314) an action (312) also is often carried out in suchembodiments by use of a hash table in the DML. Such a hash table canstore references to action object keyed by action ID, as shown in thefollowing pseudocode example. This example begins by an action service'screating a hashtable of actions, references to objects of concreteaction classes associated with a particular metric ID, using action IDsas keys. In many embodiments it is an action service that creates such ahashtable, fills it with references to action objects pertinent to aparticular metric ID, and returns a reference to the hashtable to acalling metric object.

Hashtable ActionHashTable = new Hashtable( ); ActionHashTable.put(“1”,new Action1( )); ActionHashTable.put(“2”, new Action2( ));ActionHashTable.put(“3”, new Action3( ));

Executing a particular action then can be carried out according to thefollowing pseudocode:

Action anAction = (Action) ActionHashTable.get(“2”); if (anAction !=null) anAction.take_action( );

Many examples in this specification are described as implemented withlists, often with lists of actions, for example, returned with areference to a list from an action service, for example. Lists oftenfunction in fashion similar to hashtables. Executing a particularaction, for example, can be carried out according to the followingpseudocode:

List ActionList = new List( ); ActionList.add(1, new Action1( ));ActionList.add(2, new Action2( )); ActionList.add(3, new Action3( ));

Executing a particular action then can be carried out according to thefollowing pseudocode:

Action anAction = (Action) ActionList.get(2); if (anAction != null)anAction.take_action( );

The three examples just above use switch statements, hash tables, andlist objects to explain executing actions according to embodiments ofthe present invention. The use of switch statements, hash tables, andlist objects in these examples are for explanation, not for limitation.In fact, there are many ways of executing actions according toembodiments of the present invention, as will occur to those of skill inthe art, and all such ways are well within the scope of the presentinvention.

FIG. 6 sets forth a data flow diagram illustrating an exemplary methodof executing an action. In the method of FIG. 6, executing an actionincludes identifying (380) a device class (214) representing a physicaldevice (316) administered by the action. Typical device classes includemember methods for administering the device. Typical member methods foradministering the device include member methods for getting and settingvalues of device attributes in physical devices. In the case of a lampsupporting multiple settings for light intensity, for example, a membermethod get( ) in a device class can gets from the lamp a value for lightintensity, and a member method set( ) in a device class sets the lightintensity for the lamp.

In the method of FIG. 6, executing an action includes identifying (384)a communication class (215) for the physical device (316). Tocommunicate the member methods of the device class to the physicaldevice, a communications class implements a protocol for communicatingwith a physical device. Typical communications classes include membermethods that construct, transmit, and receive data communicationsmessages in accordance with the protocol implemented by a communicationclass. The member methods in a communication class transmit and receivedata communications messages to and from a physical device. Acommunications class advantageously separates the protocols used tocommunicate with the physical device from the actions to be effected onthe device, so that a device class interface comprising get( ) and set() methods, for example, can usefully communicate with a physical deviceby use of any data communications protocol with no need to reprogram thedevice class and no need to provide one device class for eachcombination of physical device and protocol.

For further explanation, consider the following brief use case. A user'smetric sensor reads the user's heart rate at 100 beats per minute, andcreates a metric for the user having a user ID identifying the user, ametric ID identifying the metric as “heart rate,” and a metric value of100. The metric sensor transmits the user metric to the DML through aservices gateway. The DML receives the user metric and compares the usermetric with the user' metric range for resting heart rates having arange of 65-85. The DML determines that the user metric is outside thepredefined metric range. The DML uses the user ID and the metric ID toretrieve from a list an action ID for a predefined action to be executedin response to the determination that the value of the user's heart ratemetric value is outside the user's metric range for heart rate. The DMLfinds a device controlling-action ID identifying an action object havinga class name of ‘someAction,’ for example, and also having an interfacemember method known to the DML, such as the takeAction( ) methoddescribed above in the switch( ) statement.

In this example, the DML effects the action so identified by callingsomeAction.takeAction( ). The takeAction( ) method in this example isprogrammed to call a device service for a list of references to deviceobjects representing physical devices whose attributes are to beaffected by the action. The device service is programmed with a switch() statement to create in dependence upon the action ID a list ofreferences to device objects and return the device list to the callingaction object, or rather, to the calling takeAction( ) method in theaction object.

In creating the device list, the device service is programmed toinstantiate each device having a reference entered in the list, passingas a constructor parameter a reference to a communications service. Eachdevice so instantiated has a constructor programmed to call aparameterized factory method in the communications service, passing as aparameter an identification of the calling device object. Thecommunications service then instantiates and returns to the device areference to a communication object for the communications protocolneeded for that device object to communicate with its correspondingphysical device.

The principal control logic for carrying out an action typically, inembodiments of the present invention, resides in the principal interfacemethod of an action class and objects instantiated from it. In thisexample, the takeAction( ) method is programmed to carry out a sequenceof controlling method calls to carry out the changes on the physicaldevices that this action class was developed to do in the first place.The take_action( ) method carries out this work with a series of callsto accessor methods (set( ) and get( ) methods) in the device objects inits device list.

FIG. 7 is a data flow diagram illustrating an exemplary method ofdetermining (306) that the user metric (206) is outside the predefinedmetric range (210). In many embodiments of methods for administeringdevices, the user metric (206) is represented in data as a datastructure or record, such as the user metric record of FIG. 7. The usermetric (206) includes a user ID field (405), a metric ID field (407),and a value field (409).

In the example of FIG. 7, a predefined metric range for a metric isrepresented in data as a metric range such as the metric range (210) ofFIG. 7. The exemplary metric range (210) sets forth a maximum rangevalue (468) and a minimum range value (470) for a particular user for aparticular metric. The particular user and the particular metric for theexemplary range are identified respectively in a user ID field (464) anda metric ID field (462).

In the method of FIG. 7, determining (306) that value of the user metric(206) is outside of a predefined metric range (210) includes measuring(502) a degree (504) to which the user metric (206) is outside thepredefined metric range (210). In many embodiments of the presentinvention, measuring (502) the degree (504) to which the user metric(206) is outside the metric range (210) includes identifying themagnitude by which the value of the user metric is greater than themaximum metric value the metric range or the magnitude by which thevalue of the user metric value is less than the minimum value of thepredefined metric range. To the extent that measuring the degree towhich a metric is out of range includes identifying a measure as greaterthan a maximum range value or less than a minimum range value, themeasurement often advantageously includes both a magnitude and anindication of direction, such as, for example, a sign (+ or −), anenumerated indication such as, for example, ‘UP’ or ‘DOWN’, or a Booleanindication such as true for high and false for low.

In the method of FIG. 7, identifying (310) an action in dependence uponthe user metric includes identifying (512) an action in dependence uponthe degree (504) to which the value of the user metric (206) is outsidethe metric range and also often in dependence upon the direction inwhich the metric is out of range. In many embodiments of the method ofFIG. 7, identifying (512) the action in dependence upon the degree (504)to which the user metric is outside the predefined metric range includesretrieving an action ID from a metric action list (622) organized bymetric ID, user ID, degree, and direction.

In many DMLs according to the present invention are preinstalled deviceclasses for all of the devices the DML supports. Newly acquired physicaldevices identify themselves as being on the network and the DMLassociates the device ID with the device class already installed on theDML. In such an example embodiment, the DML identifies the device byassociating the device ID with the pre-installed device class.

Administering Devices in Dependence Upon User Metric Vectors IncludingDynamic Action Lists

FIG. 8 is a data flow diagram illustrating a method for administeringdevices in accordance with the present invention. The method of FIG. 8includes creating (604) a user metric vector (606) comprising aplurality of disparate user metrics (206). A user metric vectorcomprised of a plurality of disparate user metrics represents a complexindication of user condition having multiple quantifiable aspects of auser's condition and multiple quantities measuring the aspects. That is,a user metric vector is a collection of a user metrics each representinga single quantifiable aspect of a user's condition and a quantitymeasuring the aspect.

The term ‘disparate’ user metrics means user metrics of different kinds.A user metric vector (606) being comprised of a plurality of disparateuser metrics is therefore a complex indication of a user's conditioncomprising a plurality of different kinds of aspects of user conditionand plurality of quantities measuring those aspect. In many examples ofthe method of FIG. 8, the user metric vector (606) comprises referencesthe current user metric objects instantiated by a metric service.

In typical embodiments of the present invention, a user metric vector isimplemented as a user metric vector data structure or record, such asthe exemplary user metric vector (606) discussed above with reference toFIG. 3. The user metric vector (606) includes a user ID (405 on FIG. 3)identifying the user and a metric vector ID (408 on FIG. 3) uniquelyidentifying the user metric vector. The user metric vector (606) alsoincludes data storage for a metric list (652 on FIG. 3) containingreferences to disparate user metrics.

The method of FIG. 8 includes creating (605) a user metric space (610)comprising a plurality of metric ranges (210). A user metric space (610)is comprised of a plurality of disparate metric ranges for a user. Thatis, a metric space is defined by a plurality of disparate metric rangesfor a plurality of disparate metric IDs. In many exemplary embodimentsof the present invention, a metric space is implemented as a metricspace data structure such as the exemplary metric space (610) of FIG. 3including a user ID and data storage (655) for a list of references todisparate metric ranges for a user.

The method of FIG. 8 includes determining (608) whether the user metricvector (606) is outside the user metric space (610). In variousalternative example embodiments determining (608) whether the usermetric vector (606) is outside a user metric space (610) is carried outusing different methods. Methods of determining whether the user metricvector (606) is outside a user metric space (610) range in complexityfrom relatively straightforward comparison of the user metrics of themetric vector with their corresponding metric ranges of the metric spaceto more complex algorithms. Exemplary methods of determining (608)whether the user metric vector (606) is outside a user metric space(610) are described in more detail below with reference to FIG. 10.

If the user metric vector (606) is outside a user metric space (610),the method of FIG. 8 includes creating (624), in dependence upon theuser metric vector (606), a dynamic action list (626). In many examplesof the method of FIG. 8, a dynamic action list is a list of action IDscreated in dependence upon metric action lists that are associated withthe particular metrics of the user metric vector that are outside theircorresponding metric ranges of the user metric space. That is, eachmetric of the metric vector that is outside its corresponding metricrange has an associated metric action list. The associated metric actionlist includes action IDs for execution when its associated metric isoutside its corresponding metric range. A dynamic action list is anaction list including action IDs identified in dependence upon thosemetric action lists associated with the particular metrics of a usermetric vector outside their corresponding metric ranges of the usermetric space. A dynamic action list advantageously provides a list ofaction IDs tailored to the user's current condition.

In many example embodiments of the present invention, creating a dynamicaction list includes calling member methods in a dynamic action serviceobject. In many examples of the method of FIG. 8, creating a dynamicaction list includes parameterizing a member method, such ascreateDynamicActionList( ) with action IDs retrieved from action listsassociated with the particular user metrics of the user metric vectorthat are outside their corresponding metric ranges of the user metricspace. In many examples of the method of FIG. 8,createDynamicActionList( ) returns to its caller in the user metricvector a dynamic action list including action IDs identified independence upon the action IDs contained in metric action lists. Invarious alternative examples of the method of FIG. 8, a dynamic actionlist can is implemented, for example, as a hashtable, JAVA™ listcontainer, as a table in random access memory, as a SQL database tablewith storage on a hard drive or CD ROM, and in other ways as will occurto those of skill in the art.

The method of FIG. 8 includes identifying (630) at least one action(315) in the dynamic action list (626). In typical embodiments of themethod of FIG. 8, identifying an action includes retrieving from adynamic action list the identification of the action (the ‘action ID’)to be executed.

An action typically includes one or more computer programs, subroutines,or member methods that when executed, control one or more devices.Actions are typically implemented as object oriented classes andmanipulated as objects or references to objects. In fact, in thisspecification, unless context indicates otherwise, the terms ‘action,’‘action object,’ and ‘reference to an action object’ are treated more orless as synonyms. In many examples of the method of FIG. 8, an actionobject calls member methods in a device class to affect currentattributes of the physical device. In many examples of the method ofFIG. 8, action classes or action objects are deployed in OSGi bundles toa DML on a services gateway.

The method of FIG. 8 includes executing the action (614). Executing anaction therefore is often carried out in such embodiments by use of aswitch( ) statement in the DML. Such a switch( ) statement can beoperated in dependence upon the action ID and implemented, for example,as illustrated by the following segment of pseudocode:

switch (actionID) {   Case 1: actionNumber1.take_action( ); break;  Case 2: actionNumber2.take_action( ); break;   Case 3:actionNumber3.take_action( ); break;   Case 4:actionNumber4.take_action( ); break;   Case 5:actionNumber5.take_action( ); break;   // and so on } // end switch( )

The exemplary switch statement selects a particular device controllingobject for execution depending on the action ID. The device controllingobjects administered by the switch( ) in this example are concreteaction classes named actionNumber1, actionNumber2, and so on, eachhaving an executable member method named ‘take_action( ),’ which carriesout the actual work implemented by each action class.

In many examples of the method of FIG. 8, executing an action is carriedout use of a hash table in a DML. Such a hash table stores references toaction object keyed by action ID, as shown in the following pseudocodeexample. This example begins by a dynamic action list service's creatinga hashtable of actions, references to objects of concrete action classesassociated with a particular metric ID, using action IDs as keys. Inmany embodiments it is a dynamic action list service that creates such ahashtable, fills it with references to action objects pertinent to aparticular metric ID of the user metric vector outside its correspondingmetric range of the user metric space, and returns a reference to thehashtable to a calling vector object.

Hashtable DynamicActionHashTable = new Hashtable( );DynamicActionHashTable.put(“1”, new Action1( ));DynamicActionHashTable.put(“2”, new Action2( ));DynamicActionHashTable.put(“3”, new Action3( ));

Executing a particular action then can be carried out according to thefollowing pseudocode:

Action anAction = DynamicActionHashTable.get(“2”); if (anAction != null)anAction.take_action( );

Many examples of the method of FIG. 8 are also implemented through theuse of lists. Lists often function in fashion similar to hashtables.Building such a list can be carried out according to the followingpseudocode:

List DynamicActionList = new List( ); DynamicActionList.add(1, newAction1( )); DynamicActionList.add(2, new Action2( ));DynamicActionList.add(3, new Action3( ));

Executing a particular action then can be carried out according to thefollowing pseudocode:

Action anAction = DynamicActionList.get(2); if (anAction != null)anAction.take_action( );

The three examples just above use switch statements, hash tables, andlist objects to explain executing actions according to embodiments ofthe present invention. The use of switch statements, hash tables, andlist objects in these examples are for explanation, not for limitation.In fact, there are many ways of executing actions according toembodiments of the present invention, as will occur to those of skill inthe art, and all such ways are well within the scope of the presentinvention.

In some examples of the method of FIG. 8, executing an action includesidentifying a device class for the device. Typical device classesinclude member methods for administering the device. Typical membermethods for administering the device include member methods for gettingand setting values of device attributes in physical devices. In the caseof a lamp supporting multiple settings for light intensity, for example,a member method get( ) in a device class can gets from the lamp a valuefor light intensity, and a member method set( ) in a device class setsthe light intensity for the lamp.

In many examples of the method of FIG. 8, executing an action includesidentifying a communications class for the device. To communicate themember methods of the device class to the physical device, acommunications class implements a protocol for communicating with aphysical device. Typical communications classes include member methodsthat construct, transmit, and receive data communications messages inaccordance with the protocol implemented by a communication class. Themember methods in a communication class transmit and receive datacommunications messages to and from a physical device. A communicationsclass advantageously separates the protocols used to communicate withthe physical device from the actions effecting the device, so that adevice class interface comprising get( ) and set( ) methods, forexample, can usefully communicate with a physical device by use of anydata communications protocol with no need to reprogram the device classand no need to provide one device class for each combination of physicaldevice and protocol.

FIG. 9 is a data flow diagram illustrating an exemplary method ofcreating (604) a user metric vector (606) and an exemplary method ofcreating (605) a user metric space (610). In the method of FIG. 9,creating (604) a user metric vector (606) includes receiving (602) aplurality of disparate user metrics (206) having a plurality of metricvalues and a plurality of disparate metric IDs. In many embodiments ofthe method of FIG. 9, receiving (602) a plurality of disparate usermetrics (206) includes receiving disparate user metrics from one or moremetric sensors (406). In some examples of the method of FIG. 9, themetric sensor (406) reads an indication of a user's condition, creates auser metric in dependence upon the indication of a user's condition, andtransmits the user metric to a DML. In many embodiments, the metricsensor transmits the user metric to the DML in a predefined datastructure, such as the metric (206) of FIG. 3, to the DML using, forexample, protocols such as Bluetooth, 802.11, HTTP, WAP, or any otherprotocol that will occur to those of skill in the art.

In the method of FIG. 9, creating (604) a user metric vector (606)includes associating (603) the plurality of disparate user metrics (206)with the user metric vector (606). ‘Associated,’ generally in thisdisclosure and subject to context, means associated by reference. Thatis, saying that an object of one class is associated with another objectmeans that the second object possesses a reference to the first. Theobjects can be mutually associated, each possessing a reference to theother. Other relations among objects, aggregation, composition, and soon, are usually types of association, and the use of any of them, aswell as others as will occur to those of skill in the art, is wellwithin the scope of the present invention. In the exemplary method ofFIG. 9, associating (603) the plurality of disparate user metrics (206)with the user metric vector (606) is carried out by providing referencesto a plurality of disparate metric objects in the user metric vector(606).

In the method of FIG. 9, creating (604) a user metric vector (606)comprising a plurality of disparate user metrics (206) includesassociating (620) at least one metric action list (622) with eachdisparate user metric (206). In many examples of the method of FIG. 9, aplurality of metric action lists are associated with each metric of theuser vector. The action IDs included in a metric action list associatedwith a particular metric identify actions designed to administer devicesin accordance with the particular aspect of user condition representedby that metric. That is, a metric action list is tailored to affectingthe user condition represented by the metric. For example, a metric listassociated with a body temperature metric may include actions thatadminister devices such as an air conditioner, a fan, a heater,automated window shades an the like.

In many examples of the method of FIG. 9, creating a user metric vectorincludes associating a plurality of metric action lists with a singleuser metric. Some such examples of the method of FIG. 9 includeassociating one metric action list with the user metric including actionIDs for execution when the value of the user metric is above itscorresponding metric range and another metric action list includingaction IDs for execution when the value of the user metric is below itscorresponding metric range. Some examples of the method of FIG. 9 alsoinclude associating metric action lists with a user metric that includeaction IDs for execution in dependence upon the degree and directionthat the user metric is outside its corresponding metric range.

The method of FIG. 9 includes creating (605) a user metric space (610)comprising a plurality of metric ranges. In many examples of the methodof FIG. 9, a user metric space (610) is comprised of a plurality ofdisparate metric ranges that correspond in kind to the user metricscontaining in the user metric vector. In the method of FIG. 9, creating(602) a user metric space (610) includes identifying (601) a pluralityof metric ranges (210) for a plurality of disparate metrics (206) andassociating (607) the plurality of disparate metric ranges (210) for theplurality of disparate metrics (206) with the user metric space (610).

In many examples of the method of FIG. 9, identifying (601) a pluralityof metric ranges (210) and associating (607) the plurality of metricranges (210) the user metric space (610) is carried out by a metricspace service that is instantiated by a DML. The metric space servicereceives, from a user metric vector, a user metric vector ID andsearches a metric space list identified by metric vector ID for a metricspace and returns to the user metric vector a metric space IDidentifying a metric space for comparison with the user metric vector.If there is no metric space for the metric vector ID, the metric spaceservice instantiates one and stores the metric space ID in the metricspace table.

FIG. 10 is a data flow diagram illustrating two exemplary methods ofdetermining (608) whether the user metric vector (606) is outside a usermetric space (610). The first illustrated method of determining (608)whether the user metric vector (606) is outside a user metric space(610) includes comparing (806) the metric values of the metric of theuser metric vector (606) with the metric ranges (210) of the metricspace (610). In some examples of the present invention, comparing ametric value of a user metric vector with its corresponding metric rangeincludes measuring a degree to which the value of a user metric isoutside a predefined metric range and identifying if the value of theuser metric is above the predefined metric range or below the predefinedmetric range.

In many exemplary embodiments of the present invention, determiningwhether the user metric vector is outside the metric space is a functionof multiple individual comparisons between metric values and metricranges. In various alternative embodiments of the present invention,different criteria are used to identify the number of metric values thatmust be outside their corresponding metric ranges, or the degree towhich any metric value is outside its corresponding metric range todetermine that the user metric vector is outside the metric space. Insome embodiments using a strict criteria for determining if a usermetric vector is outside a user metric space, if only one metric valueis outside its corresponding metric range, then the user metric vectoris determined to be outside the metric space. In other embodiments,using less strict criteria for determining if a user metric vector isoutside a user metric space, a user metric vector is determined to beoutside the user metric space if all of the metric values of the usermetric vector are outside their corresponding metric ranges by a certaindegree. In various embodiments, the number of metric values that must beoutside their corresponding metric ranges, or the degree to which ametric must be outside its corresponding metric range to make adetermination that the user metric vector is outside the metric spacewill vary, all such methods of determining whether a user metric vectoris outside a metric space are well within the scope of the presentinvention.

The second illustrated method of determining (608) that the user metricvector (606) is outside the user metric space (610) illustrated in FIG.10 includes calculating (810) a metric vector value (812) andcalculating (814) a metric space value (816) and comparing (818) themetric vector value (812) to the metric space value (816). One way ofcalculating a metric vector value is by using a predetermined formula toidentify a single value that is a function of the metric values of theuser metric vector. In one exemplary embodiment of the presentinvention, calculating a metric vector value includes averaging themetric values of the user metric vector. In another example embodiment,calculating a metric vector value includes prioritizing certain kinds ofmetrics and using a weighted average based on the priority of the metricto calculate a metric vector value.

In some exemplary embodiments, calculating (814) a metric space value(816) includes using a predetermined formula to determine a metric spacevalue that is a function of the minimum and maximum values of eachmetric range of the user metric space. In one example embodiment,calculating a metric space value includes finding the center point ofthe minimum and maximum value of the each metric range and thenaveraging the center points.

The illustrated method includes comparing (818) the metric space value(816) and the metric vector value (812). In various embodiments of thepresent invention, how the metric vector value and the metric spacevalue are compared to determine whether the metric vector is outside themetric space will vary. In one example embodiment, the metric vectorvalue is subtracted from the metric space value. If the result of thesubtraction is within a predetermined range, then the user metric vectoris determined to be within the metric space. In the same example, if theresult of the subtraction is not within the predetermined range, thenthe metric vector value is not determined to be within the metric space.

The illustrated methods of FIG. 10 are provided for explanation and notfor limitation. There are many other ways metric ranges and metricvalues can be compared, combined, manipulated, or otherwise used to makea determination that a user metric vector is outside a metric space. Allsuch ways of comparing, combining, manipulating, or otherwise usingmetric values and metric ranges to make a determination that a usermetric vector is outside a metric space are included within the scope ofthe present invention.

FIG. 11 is a data flow diagram illustrating an exemplary method ofcreating (624), in dependence upon the user metric vector (606), adynamic action list (626). Typical dynamic action lists include actionIDs identified dynamically in dependence upon the action IDs includedwithin metric action lists associated with the particular metrics of auser's metric vector that are outside their corresponding metric rangesof the user's metric space. Creating such a dynamic action listadvantageously provides a set of action IDs tailored to administerdevices in response to the user's current condition.

In the method of FIG. 11, creating (624), in dependence upon the usermetric vector (606), a dynamic action list (626) includes identifying(752) a metric action list (622) for each user metric (206) of the usermetric vector (606) having a value that is outside a metric range (210)of the user metric space (610). In many examples of the method of FIG.11, identifying (752) a metric action list (622) for each user metric(206) that is outside its corresponding a metric range (210) includesretrieving a reference to the metric action list from a metric objectpreviously identified as being outside its corresponding metric rangewhen the user metric vector was determined to be outside the user metricspace. The metric objects outside their metric ranges are, in manyexamples, identified when the metric objects are compared with theirmetric ranges to determine if the user metric vector is outside themetric space.

In many examples of the method of FIG. 11, a metric has a plurality ofassociated metric action lists. Each associated metric action listincludes a set of action IDs for execution in dependence upon the degreeand direction that the value of the metric is outside the metric range.In some examples of the method of FIG. 11 therefore, identifying (752) ametric action list (622) for each user metric (206) of the user metricvector (606) having a value that is outside a metric range (210) of theuser metric space (610) includes identifying a metric list in dependenceupon a degree to which the value of each user metric of the user metricvector is outside a metric range of the user metric space. In anotherexample of the method of FIG. 11, identifying (752) a metric action list(622) for each user metric (206) of the user metric vector (606) havinga value that is outside a metric range (210) of the user metric space(610) includes identifying a metric list in dependence upon a directionthat the value of each user metric of the user metric vector is outsidea metric range of the user metric space.

In the method of FIG. 11, creating (624), in dependence upon the usermetric vector (606), a dynamic action list (626) includes retrieving(754) at least one action ID (315) from each metric action list (622).Some metric action lists include a plurality of action IDs and thereforemany examples of the method of FIG. 11 include retrieving a plurality ofaction IDs from the metric action lists associated with each metrichaving a value outside its corresponding metric range.

In the method of FIG. 11, creating (624), in dependence upon the usermetric vector (606), a dynamic action list (626) includes identifying(756) at least one action ID (315) for inclusion in the dynamic actionlist (626) in dependence upon the action IDs (315) retrieved from themetric action lists (622). In many examples of the method of FIG. 11,identifying (756) at least one action ID (315) for inclusion in thedynamic action list (626) in dependence upon the action IDs (315)retrieved from the metric action lists (622) includes identifying anaction ID retrieved directly from the metric action lists themselves forinclusion in the dynamic action list. That is, in some examples of themethod of FIG. 11 the same action ID retrieved from a metric action listis included in the dynamic action list.

In the method of FIG. 11, identifying (756) at least one action ID (315)for inclusion in the dynamic action list (626) in dependence upon theaction IDs (315) retrieved from the metric action lists (622) includescomparing (758) the action IDs (315) of the metric action lists (622)and omitting repetitious actions. In some examples of the method of FIG.11, omitting repetitious actions includes determining that the sameaction ID is included in more than one metric action list. In suchexamples, creating a dynamic action list includes identifying metricaction lists having the same action IDs and including the action ID onlyonce in the dynamic action list.

In the method of FIG. 11, identifying (756) at least one action ID (315)for inclusion in the dynamic action list (626) in dependence upon theaction IDs (315) retrieved from the metric action lists (622) includesretrieving (760) an action ID (315) from a dynamic action table (762) independence upon at least one action ID of the metric action lists. Inmany examples of the method of FIG. 11, a dynamic action table (762) isa data structure including action IDs indexed by other action IDs. Thatis, the dynamic action table is a data structure designed to indexpredetermined action IDs for inclusion in the dynamic action list independence upon the action IDs retrieved from the metric action lists.

Such a dynamic action table therefore is in many examples of the methodof FIG. 11 designed to identify conflicting actions retrieved from themetric action lists, identify superseding actions retrieved from themetric action list, as well as identify further actions not included inthe metric action lists. In some examples of the method of FIG. 11,identifying (756) at least one action ID (315) for inclusion in thedynamic action list (626) in dependence upon the action IDs (315)retrieved from the metric action lists (622) includes omittingconflicting actions. In many examples of the method of FIG. 11 a dynamicaction table is used to identify action IDs that have been predeterminedto conflict. For example, an action ID included in one metric actionlist that identifies a device controlling action to turn on a ceilingfan conflicts with an action ID identifying a device controlling actionto turn off the same ceiling fan. Such conflicting action IDs areomitted from the dynamic action list.

In some examples of the method of FIG. 11, identifying (756) at leastone action ID (315) for inclusion in the dynamic action list (626) independence upon the action IDs (315) retrieved from the metric actionlists (622) includes omitting superseded actions. A superseded action isan action that when executed administers the same device in the samedirection as another superseding action, but administers the device to alesser degree than the other superseding action. That is, an action issuperseded when another action administers the same device to a greaterdegree such that the execution of superseded action is cloaked byexecution of the superseding action. For example, the execution of anaction ID that results in changing the value of a current attribute of aceiling fan from “5” to “4” is superseded by the execution of an actionID that results in changing the same ceiling fan attribute from “5” to“2.” In many examples of the method of FIG. 11, a dynamic action tableis used to identify action IDs that have been predetermined to supersedeother actions IDs. Many examples of the method of FIG. 11 includeomitting the superseded action IDs from the dynamic action list andincluding the superseding action ID.

In the method of FIG. 11, identifying (756) at least one action ID (315)for inclusion in the dynamic action list (626) in dependence upon theaction IDs (315) retrieved from the metric action lists (622) includesidentifying an action ID for inclusion in the dynamic action list thatis not included in any of the identified metric action lists (622). Inmany examples of the method of FIG. 11, an action ID identified by alookup in the dynamic action table (762) is not included in any of theidentified metric action. In some of these examples, the dynamic actiontable is populated with action IDs that have been predetermined toaffect the same user condition when executed as other action IDs. Such adynamic action table is indexed to identify an action ID for executionwhen one or more other action IDs are retrieved from the metric actionlists. In this way, dynamic action tables advantageously provide avehicle for identifying and executing more actions to affect the user'scurrent condition.

For further explanation of identifying action IDs that are not includedin any metric action list associated with a user metric outside itscorresponding range, the following example is provided. Two user metricsof a user metric vector are above their corresponding metric ranges ofthe user's metric space. The first metric represents body temperatureand has a first action ID in its associated metric action list that whenexecuted results in turning on a ceiling fan. The second metricrepresents heart rate and has a second action ID in its associatedmetric list that when executed turns on an air conditioner. A lookup ina dynamic action table in dependence upon the first action ID and thesecond action ID retrieves a third action ID that is not included ineither metric action list of either metric. Executing the third actionID results in turning on the ceiling fan, turning on the airconditioner, and drawing automated window curtains. The added action ofdrawing automated window curtains is predetermined to affect the sameuser condition as turning on the air conditioner and the ceiling fan. Alookup on the dynamic action table identifies the third action ID forinclusion in the dynamic action list in dependence upon the first andsecond action IDs.

Administering Devices Including Allowed Action Lists

The previous sections of this disclosure discussed administering deviceswith actions identified in dependence upon user metrics and user metricvectors. In some situations however, a particular action may beavailable for execution, but for one reason or another, it has beendetermined that the action should not be executed. Consider the exampleof a hotel providing a DML in each room to administer devices inaccordance with the methods of FIG. 5 and FIG. 8. While each room DMLhas installed upon it actions that control the room's air conditioningunit in dependence upon user metrics, the hotel has an interest inlimiting the amount of electricity consumed by the room's airconditioning unit. To address this situation and others, the followingsection describes a method for administering devices that includesallowed action lists with reference to FIG. 12.

FIG. 12 is a data flow diagram illustrating an exemplary method foradministering devices in a network. The method includes creating (702) auser metric vector (606) including a plurality of disparate user metrics(206). As discussed above with reference to FIG. 8 and FIG. 9, a usermetric vector is a collection of a user metrics each representing asingle quantifiable aspect of a user's condition and a quantitymeasuring the aspect. In typical embodiments of the present invention, auser metric vector is implemented as a user metric vector data structureor record, such as the exemplary user metric vector (606) discussedabove with reference to FIG. 3. In many examples of the method of FIG.12, creating (702) a user metric vector (606) including a plurality ofdisparate user metrics (206) includes receiving a plurality of disparateuser metrics from a metric sensor worn by the user, associating metricaction lists with those user metrics, and associating those user metricswith a user metric vector.

The method of FIG. 12 includes creating (704) a user metric space (610)including a plurality of metric ranges (210). As discussed above withreference to FIG. 8 and FIG. 9, user metric space (610) is comprised ofa plurality of disparate metric ranges for a user. A user metric spacecan be implemented as a metric space data structure such as theexemplary metric space (610) of FIG. 3. In many examples of the methodof FIG. 12, creating (704) a user metric space (610) including aplurality of metric ranges (210) includes identifying a plurality ofmetric ranges for a plurality of disparate metrics for the user andassociating the plurality of disparate metric ranges for the pluralityof disparate metrics with a user metric space.

The method of FIG. 12 includes determining (706) whether the user metricvector (606) is outside the user metric space (610). Two ways ofdetermining (706) whether the user metric vector (606) is outside theuser metric space (610) are described above with reference to FIG. 10.One way of determining (706) whether the user metric vector (606) isoutside the user metric space (610) includes directly comparing themetric values of the metric of the user metric vector with the metricranges of the metric space and deciding based on the direct comparisonwhether the user metric vector is within the user metric space. Anotherway of determining (706) whether the user metric vector (606) is outsidethe user metric space (610) includes calculating a metric vector value,calculating metric space value, and comparing the metric vector value tothe metric space value. There are many other ways metric ranges andmetric values can be compared, combined, manipulated, or otherwise usedto make a determination that a user metric vector is outside a metricspace. All such ways of comparing, combining, manipulating, or otherwiseusing metric values and metric ranges to make a determination that auser metric vector is outside a metric space are included within thescope of the present invention.

If the user metric vector (606) is outside a user metric space (610),the method of FIG. 12 includes identifying (708) an action in dependenceupon the user metric vector. An action typically includes one or morecomputer programs, subroutines, or member methods that when executed,control one or more devices. Actions are typically implemented as objectoriented classes and manipulated as objects or references to objects.Action objects typically call member methods in a device class to affectcurrent attributes of the physical device installed in the domain. Oneway of identifying an action discussed above with reference to FIG. 5 isby retrieving an action ID from an action list. Another way ofidentifying an action discussed above with reference to FIG. 8 and FIG.11 includes creating a dynamic action list. The two methods ofidentifying an action are provided for explanation not for limitation,and other ways of identifying an action are well within the scope of thepresent invention.

The method of FIG. 12 includes receiving (709) an allowed action list(714). Allowed action list (714) is a list of action IDs that arecurrently designated as allowable for execution. That is, actions thatare allowed to be executed. In many examples, an allowed action list isimplemented as a JAVA™ list container, a hash table, or any other datastructure that will occur to those of skill in the art.

In the method of FIG. 12, the allowed action list (714) is received froma moderator DML (700) across a network. In some such examples, theuser's DML (108) receives an allowed list from a moderator DML byperiodically requesting an allowed action list from the moderator DML.In other examples, the moderator DML periodically pushes an allowedaction list to the DML (108). The architecture of FIG. 12 is applicableto the situation arising in a multi-DML hotel described briefly above.In such an example, each room's DML receives from the moderator DML anallowed action list defining the actions allowed for execution on theuser's behalf in the room.

The method of FIG. 12 includes determining (710) whether the action(315) is allowed. In many examples of the method of FIG. 12, determining(710) whether the action (315) is allowed includes comparing theidentified action ID with the allowed action list. If the identifiedaction ID is contained within the allowed action list, the identifiedaction ID is allowed. If the identified action is not contained withinthe allowed action list, the identified action is not allowed.

If the action (315) is allowed, the method of FIG. 12 includes executing(712) the action (315). Three ways of executing an action are describedabove with reference to FIG. 8 including using switch statements, JAVA™lists, and hash tables. The examples using switch statements, hashtables, and list objects to explain executing actions are provided forexplanation, not for limitation. In fact, there are many ways ofexecuting actions according to embodiments of the present invention, aswill occur to those of skill in the art, and all such ways are wellwithin the scope of the present invention.

If the identified action is not allowed, the method of FIG. 12 includesidentifying (716) an allowed replacement action (718). In some examplesof the method of FIG. 12, identifying (716) an allowed replacementaction (718) includes looking up a replacement action in the allowedaction list in dependence upon the identified action ID. In many suchexamples, the allowed action list (714) includes replacement action IDsindexed by other action IDs. In such cases, a replacement action ID isretrieved from the allowed action list in dependence upon the action ID(315) of the identified action.

The method of FIG. 12 includes executing (720) the allowed replacementaction (718). Three ways of executing an action are described above withreference to FIG. 8 including using switch statements, JAVA™ lists, andhash tables. The examples using switch statements, hash tables, and listobjects to explain executing actions are provided for explanation, notfor limitation. In fact, there are many ways of executing actionsaccording to embodiments of the present invention, as will occur tothose of skill in the art, and all such ways are well within the scopeof the present invention.

As a further aid to understanding the following use case is provided. Ahotel includes DMLs in each room and a single moderator DML that iscoupled for data communications with each room DML. The moderator DMLpushes a new allowed action list to each room DML twice daily. The firstallowed action list is pushed to the room DMLs at 10:00 am and includesaction IDs that control the air conditioning units thermostat allowing aminimum setting of 65 degrees Fahrenheit and other action IDs thatcontrol the settings on a ceiling fan allowing a maximum setting on aceiling fan to be the fan's maximum rate of speed. The second allowedaction list is pushed to the room DMLs at 8:00 pm and includes actionIDs that control the air conditioning units thermostat allowing aminimum setting of 70 degrees Fahrenheit and other action IDs thatcontrol the settings on a ceiling fan allowing the maximum setting onthe ceiling fan to be the fan's minimum rate of speed.

A user is in one of the hotel rooms. When a user's metric vector isoutside the user's metric space because the user's body temperaturemetric is beyond the maximum value of the user's body temperature metricrange, an action is identified that lowers the air conditioner to 65degrees and sets the ceiling fan to the maximum setting. If the time is5:00 pm, the room's DML identifies that the action is allowed bycomparing the identified action ID with the current allowed action listand the action is executed. If the time is 10:00 pm, the room's DMLidentifies that the action is not allowed, and retrieves a replacementaction from the allowed action list. The replacement action lowers thethermostat to the allowed 70 degrees Fahrenheit and sets the ceiling fanto the allowed minimum rate of speed.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

1. A method for administering devices in a network, the methodcomprising: creating a user metric vector comprising a plurality ofdisparate user metrics, each user metric comprising an indication of adynamic change in a user's physical condition in response to an externalstimulus, each user metric further comprising a field identifying theuser, a field identifying an aspect of the user's physical conditionthat the user metric represents, and a field storing a value of theaspect of the user's physical condition that the user metric represents,wherein the user comprises a person; creating a user metric spacecomprising a plurality of metric ranges; determining whether the usermetric vector is outside the user metric space; if the user metricvector is outside a user metric space, identifying an action independence upon the user metric vector, the action administering adevice via the network to alter the user's physical condition inresponse to the external stimulus; determining whether the action isallowed; if the action is allowed, executing the action; and if theaction is not allowed, identifying an allowed replacement action andexecuting the allowed replacement action.
 2. The method of claim 1wherein determining whether the action is allowed comprises comparingthe identified action with an allowed action list.
 3. The method ofclaim 1 wherein identifying an allowed replacement action comprisescomparing the identified action with an allowed action list.
 4. Themethod of claim 1 comprising receiving an allowed action list.
 5. Asystem for administering devices in a network, the system comprising:means for creating a user metric vector comprising a plurality ofdisparate user metrics, each user metric comprising an indication of adynamic change in a user's physical condition in response to an externalstimulus, each user metric further comprising a field identifying theuser, a field identifying an aspect of the user's physical conditionthat the user metric represents, and a field storing a value of theaspect of the user's physical condition that the user metric represents,wherein the user comprises a person; means for creating a user metricspace comprising a plurality of metric ranges; means for determiningwhether the user metric vector is outside the user metric space; if theuser metric vector is outside a user metric space, means for identifyingan action in dependence upon the user metric vector, the actionadministering a device via the network to alter the user's physicalcondition in response to the external stimulus; means for determiningwhether the action is allowed; if the action is allowed, means forexecuting the action; and if the action is not allowed, means foridentifying an allowed replacement action and executing the allowedreplacement action.
 6. The system of claim 5 wherein means fordetermining whether the action is allowed comprises means for comparingthe identified action with an allowed action list.
 7. The system ofclaim 5 wherein means for identifying an allowed replacement actioncomprises means for comparing the identified action with an allowedaction list.
 8. The system of claim 5 comprising means for receiving anallowed action list.
 9. A computer program product for administeringdevices in a network, the computer program product comprising: arecording medium; means, recorded on the recording medium, for creatinga user metric vector comprising a plurality of disparate user metrics,each user metric comprising an indication of a dynamic change in auser's physical condition in response to an external stimulus, each usermetric further comprising a field identifying the user, a fieldidentifying an aspect of the user's physical condition that the usermetric represents, and a field storing a value of the aspect of theuser's physical condition that the user metric represents, wherein theuser comprises a person; means, recorded on the recording medium, forcreating a user metric space comprising a plurality of metric ranges;means, recorded on the recording medium, for determining whether theuser metric vector is outside the user metric space; if the user metricvector is outside a user metric space, means, recorded on the recordingmedium, for identifying an action in dependence upon the user metricvector, the action administering a device via the network to alter theuser's physical condition in response to the external stimulus; means,recorded on the recording medium, for determining whether the action isallowed; if the action is allowed, means, recorded on the recordingmedium, for executing the action; and if the action is not allowed,means, recorded on the recording medium, for identifying an allowedreplacement action and executing the allowed replacement action.
 10. Thecomputer program product of claim 9 wherein means, recorded on therecording medium, for determining whether the action is allowedcomprises means, recorded on the recording medium, for comparing theidentified action with an allowed action list.
 11. The computer programproduct of claim 9 wherein means, recorded on the recording medium, foridentifying an allowed replacement action comprises means, recorded onthe recording medium, for comparing the identified action with anallowed action list.
 12. The computer program product of claim 9comprising means, recorded on the recording medium, for receiving anallowed action list.